Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1699

reference
657-tree-1
name
1699
tree-preservation-order

undefined

657-tpo-1
uprn
address-text
point
POINT (-1.006982 50.863136)
geometry
MULTIPOLYGON (((-1.006925 50.863130,-1.006928 50.863141,-1.006935 50.863151,-1.006948 50.863159,-1.006964 50.863164,-1.006981 50.863166,-1.006999 50.863165,-1.007015 50.863160,-1.007027 50.863152,-1.007036 50.863142,-1.007039 50.863131,-1.007036 50.863120,-1.007028 50.863110,-1.007016 50.863102,-1.007000 50.863096,-1.006983 50.863094,-1.006965 50.863096,-1.006949 50.863101,-1.006936 50.863109,-1.006928 50.863119,-1.006925 50.863130)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL